Many Google Cloud customers want to connect
their Google Virtual Private Cloud networks to other networks in their system,
such as on-premises networks or networks in other clouds. There are several effective ways to accomplish
this. One option is to start with a Virtual Private
Network connection over the internet and use Cloud VPN to create a “tunnel” connection. To make the connection dynamic, a Google Cloud
feature called Cloud Router can be used. Cloud Router lets other networks and Google
VPC, exchange route information over the VPN using the Border Gateway Protocol. Using this method, if you add a new subnet
to your Google VPC, your on-premises network will automatically get routes to it. But using the internet to connect networks
isn't always the best option for everyone, either because of security concerns or because
of bandwidth reliability. So, a second option is to consider “peering”
with Google using Direct Peering. Peering means putting a router in the same
public data center as a Google point of presence and using it to exchange traffic between networks. Google has more than 100 points of presence
around the world. Customers who aren’t already in a point
of presence can work with a partner in the Carrier Peering program to get connected. Carrier peering gives you direct access from
your on-premises network through a service provider's network to Google Workspace and
to Google Cloud products that can be exposed through one or more public IP addresses. One downside of peering, though, is that it
isn’t covered by a Google Service Level Agreement. If getting the highest uptimes for interconnection
is important, using Dedicated Interconnect would be a good solution. This option allows for one or more direct,
private connections to Google. If these connections have topologies that
meet Google’s specifications, they can be covered by an SLA of up to 99.99%. Also, these connections can be backed up by
a VPN for even greater reliability. Another option we’ll explore is Partner
Interconnect, which provides connectivity between an on-premises network and a VPC network
through a supported service provider. A Partner Interconnect connection is useful
if a data center is in a physical location that can't reach a Dedicated Interconnect
colocation facility, or if the data needs don’t warrant an entire
10 GigaBytes per second connection. Depending on availability needs, Partner Interconnect
can be configured to support mission-critical services or applications that can tolerate
some downtime. As with Dedicated Interconnect, if these connections
have topologies that meet Google’s specifications, they can be covered by an SLA of up to 99.99%,
but note that Google isn’t responsible for any aspects of Partner Interconnect provided
by the third-party service provider, nor any issues outside of Google's network. And the final option is Cross-Cloud Interconnect. Cross-Cloud Interconnect helps you establish
high-bandwidth dedicated connectivity between Google Cloud and another cloud service provider. Google provisions a dedicated physical connection
between the Google network and that of another cloud service provider. You can use this connection to peer your Google
Virtual Private Cloud network with your network that's hosted by a supported cloud service
provider. Cross-Cloud Interconnect supports your adoption
of an integrated multicloud strategy. In addition to supporting various cloud service
providers, Cross-Cloud Interconnect offers reduced complexity, site-to-site data transfer,
and encryption. Cross-Cloud Interconnect connections are available
in two sizes: 10 Gbps or 100 Gbps.